This is a productivity-sapping issue I've encountered for some time now. I'm doing data analysis and working with several QueryDefs at a time. Just when I get deep into my work I have to close everything and start over.

I have:

• Access 2013 (15.0.4745.1000) MSO (15.0.4745.1000) 64-bit
• Windows 10 Pro (Version 10.0.10240 Build 10240)
• Surface Pro 3 with 8GB RAM and Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 2301 MHz, 2 Core(s), 4 Logical Processor(s)
• BIOS Version/Date American Megatrends Inc. 3.11.0950, 6/5/2015

The scenario: I am working in any accdb desktop database. I open several Access queries and tables at once (doing data mapping, comparisons, analysis, etc.). Then I step away and Windows sleeps. After it wakes up, the next time I go to design view on one of my several still-open queries, it shows this error ("There isn't enough free memory to update the display. Close unneeded programs and try again."). There is no lack of free memory on the machine, and only a few other programs are open at the time. After I click OK, the query is displayed in design view but some fields in the grid that contain values appear to be blank. If I click on such a cell, the content becomes visible, and editable, but when I click away, that cell goes blank again. I am able to move between SQL and datasheet view without problems, but design view begins to always show the error, eventually reaching the point where the grid appears blank. After that, I want to close all my queries, but the control menus to close the windows stop responding, so I have to use the keyboard shortcut (ctrl-F4) to trigger the "save?" dialog. If I keep going until things get really bad, the tiles on the Windows 10 start menu also begin to go blank. Reinstalling Office or using a new accdb file doesn't make any difference at all. These accdb files have no VBA or macros - just tables and queries.

I interpret this as Access leaking "system resources", if I remember the term correctly, which I think refers to a specific little piece of memory that Windows uses to store the properties of graphics objects for the UI (e.g. icons, buttons, grid cell, windows, etc.), consisting of object sizes, screen locations, icons and text for quick display if and when it needs to be displayed. 

MY SPECULATION about what is happening: On system wake up, and also on changing an open query to design view after having made changes in SQL view, Access forgets its previously-allocated system resources for the cells of the QueryDef's QBE grid and requests new ones, eventually exhausting Windows' available system resources, so that Windows begins refusing to store more. The cell I am currently editing can be rendered, but it can't be saved for display once the focus moves away from it.

Questions: Is this a leak in Access itself or in something else, e.g. in a display driver? I've seen it happen with or without the use of external monitors. Can anyone suggest how to fix it or to better document it for investigation by the appropriate team?

Rick

try this:

Reset the registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\Access Connectivity Engine\Engines\ACE]
MaxBufferSize = 1024

I found this inserting kb https://support.microsoft.com/en-us/kb/3055016 you'd better try it.

KR